Combined base transceiver station and base station controller call origination and termination

ABSTRACT

A system, method, and computer readable medium for a mobile origination comprises receiving an origination request message by a main call control (MCC) from a radio call control (RCC), receiving an assignment request message by the RCC from the MCC, receiving a traffic channel assign message by a channel element control (CEC) and by the MCC from the RCC, receiving a call setup message by a selector distribution unit (SDU) from the MCC, and receiving a link active message by the CEC from the SDU.

CROSS REFERENCE TO RELATED APPLICATIONS

The present patent application is a continuation of and claims priorityfrom patent application Ser. No. 12/632,920, filed on Dec. 8, 2009 andtitled COMBINED BASE TRANSCEIVER STATION AND BASE STATION CONTROLLERCALL ORIGINATION AND TERMINATION, now issued U.S. Pat. No. 8,472,964,issued on Jun. 25, 2013, which is a continuation of application Ser. No.11/037,813, filed on Jan. 18, 2005 and titled COMBINED BASE TRANSCEIVERSTATION AND BASE STATION CONTROLLER CALL ORIGINATION AND TERMINATION,now issued U.S. Pat. No. 7,647,054, issued on Jan. 12, 2010, which inturn claims the benefit of provisional patent application No.60/537,408, filed on Jan. 16, 2004, entitled CDMA Radio Access NetworkSystem and Method, and provisional patent application No. 60/537,419,filed on Jan. 16, 2004, entitled CDMA IP Base Transceiver Station, thecontents of which are enclosed by reference herein. The present patentapplication is further related to patent application Ser. No.11/037,063, entitled COMBINED BASE TRANSCEIVER STATION AND BASE STATIONCONTROLLER, now issued U.S. Pat. No. 8,060,143, issued on Nov. 15, 2011,application Ser. No. 11/037,814 entitled COMBINED BASE TRANSCEIVERSTATION AND BASE STATION CONTROLLER HANDOFF, now issued U.S. Pat. No.8,019,348, issued on Sep. 13, 2011, application Ser. No. 11/037,386entitled COMBINED BASE TRANSCEIVER STATION AND BASE STATION CONTROLLERDATA CALL, now issued U.S. Pat. No. 7,509,128, issued on Mar. 24, 2009,application Ser. No. 11/037,387 entitled COMBINED BASE TRANSCEIVERSTATION AND BASE STATION CONTROLLER DATA CALL AND QUALITY OF SERVICE,now issued U.S. Pat. No. 7,643,449, issued on Jan. 5, 2010, and patentapplication Ser. No. 11/037,388 entitled COMBINED BASE TRANSCEIVERSTATION AND BASE STATION CONTROLLER OPTIMIZED ASSIGNMENT OF FRAMEOFFSETS, now issued U.S. Pat. No. 8,090,370, issued on Jan. 3, 2012,each of which is assigned to the assignee of the present invention.

BACKGROUND OF THE INVENTION

The present invention is related to a base transceiver station and abase station controller, and, more specifically to a combined basetransceiver station and a base station controller.

Current cellular operators predominantly provide services via very largeor macro coverage areas. Limitations encountered by these operatorsinclude the difficulty of providing reliable in-building or campuscoverage. Such coverage should provide subscribers with seamlessservices at a particular quality level, and should provide operatorswith additional revenue sources.

Therefore, what is needed is a wireless solution that overcomes theaforementioned limitations by providing a micro solution thatcompliments the wireless macro network by providing increased voice anddata capacity and coverage.

SUMMARY OF THE INVENTION

The present invention provides a radio access network (RAN) system(which contains a base transceiver station and a base station controllerintegrated into a single compact platform) for wireless coverage andin-building services, as well as for providing additional capacity in amacro network when it comes to filling “hotspots.” Such a RAN system,which preferably operates in or in conjunction with a CDMA network,supports signaling, traffic, handoff, power, and control, whileproviding multiple interfaces to the core network.

In one embodiment, a method for a mobile origination comprises receivingan origination request message by a main call control (MCC) from a radiocall control (RCC), receiving an assignment request message by the RCCfrom the MCC, receiving a traffic channel assign message by a channelelement control (CEC) and by the MCC from the RCC, receiving a callsetup message by a selector distribution unit (SDU) from the MCC, andreceiving a link active message by the CEC from the SDU.

In another embodiment, a method for a mobile origination comprisesreceiving an origination request message by a base station controller(BSC) from a base transceiver station (BTS), wherein the BSC and the BTSare co-located, receiving an assignment request message by the BTS fromthe BSC, receiving a traffic channel assign message by the BTS and theBSC, receiving a call setup message by the BSC from the BSC, andreceiving a link active message by the BTS from the BSC.

In a further embodiment, a combined base station controller (BSC) andbase transceiver station (BTS) system for mobile origination comprisesthe BSC adapted to receive an origination request message, the BTSadapted to receive an assignment request message, the BTS and the BSCadapted to receive a traffic channel assign message, the BSC adapted toreceive a call setup message, and the BTS adapted to receive a linkactive message.

In yet another embodiment, a computer readable medium comprisesinstructions for: receiving mobile station identification information bya first module, allocating radio resources by a second module, assigningforward and reverse traffic channel elements by the first module,receiving mobile station information and initialization information bythe second module, and indicating a link between the first module andthe second module has been established.

In yet a further embodiment, a method for a mobile termination comprisesreceiving a paging request message by a radio call control (RCC) from amain call control (MCC), receiving a page response message by the RCCand by the MCC, receiving an assignment request message by the MCC andby the RCC, and receiving a traffic channel assign message by a channelelement control (CEC).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a radio access network (RAN) in accordance with apreferred embodiment of the present invention;

FIG. 2 depicts a stackable RAN in accordance with a preferred embodimentof the present invention;

FIG. 3 depicts a further stackable RAN in accordance with a preferredembodiment of the present invention;

FIG. 4 depicts a mobile origination message flow in accordance with apreferred embodiment of the present invention;

FIG. 5 depicts a mobile termination message flow in accordance with apreferred embodiment of the present invention; and

FIGS. 6A and 6B depicts a mobile to mobile call setup and releasemessage flow in accordance with a preferred embodiment of the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to FIG. 1, radio access network (RAN) 10 comprises a basestation controller (BSC) 12 and a base transceiver station (BTS) 14 thatcomprise a number of blocks or modules. These blocks or modules aresoftware, hardware, firmware, and/or a combination of software,hardware, and/or firmware. The BSC 12 comprises a selector distributionunit (SDU) 20 coupled to a main call control (MCC) 22 and to a packetcontrol function (PCF) 24 which is also coupled to the MCC 22, asignaling control connection part (SCCP) 26 coupled to aninteroperability system (IOS) 28 which is also coupled to the MCC 22, acall agent simulator (CA_SIM) 30 which is coupled to the SCCP 26, and anoperation, administration, and maintenance (OA&M) 32 module coupled tothe PCF 24.

Main Call Control (MCC) 22

The MCC 22, which performs the operations that pertain to individualsubscribers including registration, call setup, call release, handoffand other subscriber features, is associated with the followingfunctionality:

Registration

Mobile registration is a process where mobile characteristics such aslocation or status are provided to the network. Registration may beinitiated by a mobile station (MS, not shown), by a network, or impliedduring access by the MS. To support these features, the MCC 22interfaces with a radio call control module (RCC) 18, which will bedescribed further below, and with a call agent (CA) 104. The CA 104 ispreferably a soft switch whose functions include call processing,supplementary service, registration, interacts with a Home LocationRegister (HLR) in the macro network, and provides common PBX functions.

Mobile Originated Call Setup for Voice and Circuit Data Calls

The MCC 22 receives an Origination Message from the MS via the RCC 18and then communicates with CA 104 to request call service, confirm thevalidity of the MS, as well as get the resource information from a mediagateway (MG, not shown). The MG mediates the elements between circuitswitched voice networks and an IP network. For example, the MG relaysvoice, fax, modem and data traffic over the IP network. The MCC 22interfaces with the RCC 18 to request a radio resource and with the SDU20 to allocate a selector resource.

Mobile Terminated Call Setup for Voice and Calls and Circuit Data Calls

The MCC 22 receives a Paging Request message from the CA 104 and passesit to the RCC 18 to initiate a mobile terminated call setup scenario.The MCC 22 receives a Page Response Message then communicates with theCA 104 to get the resource information from the MG and indicate for thecall to be answered at the MS. The MCC 22 interfaces with the RCC 18 torequest a radio resource and with the SDU 20 to allocate a selectorresource.

Call Clearing of Voice and Circuit Data Calls

Call clearing may be initiated by either the MS, the SDU 20 or the CA104. The MCC 22 sends clear messages to the SDU 20 or to the CA 104 andreleases internal resources.

Mobile Originated Call Setup for Packet Data Calls

The MCC 22 receives an Origination Message from the MS via the RCC 18with a data rate to send set to ‘true’ (DRS=1) and a packet data serviceoption, and then communicates with the CA 104 to request packet dataservice and confirm the validity of the MS. The MCC 22 interfaces withthe PCF 24 to setup a connection to a packet data serving node (PDSN)101, which exchanges packets with the MS over the radio and the other IPnetworks, with the RCC 18 to requests a radio resource, and with the SDU20 to allocate a selector resource.

Reactivation of Packet Data Calls

The MCC 22 supports either the MS initiated or network initiatedreactivation from a dormant state. With a MS initiated reactivation, anormal packet data call setup procedure in the MCC ensues, while with anetwork initiated reactivation, the MCC 22 sends a base station (BS, notshown) Service Request to the CA 104 to begin an initiated call setup asa request from the PCF 24. The BS, which is a fixed station thatcommunicates with the MS, may be a cell, a sector within a cell, amobile switching center (MSC), or other part of the wireless system.

Call Clearing of Packet Data Calls

Call clearing may be initiated by either the MS, the SDU 20, the CA 104or the PCF 24. During a call clearing scenario, the MCC 22 sends clearmessages to the SDU 20, the CA 104 and the PCF 24 and releases internalresources.

Transition to Dormancy for Packet Data Calls

If the MS transits to a Dormant State, the MCC 22 proceeds in a normalpacket call release scenario and notifies the CA while setting therelease cause to “packet call going dormant.” The MCC 22 also supportsDormant Handoff.

Short Data Bursts

The MCC 22 supports a Short Data Burst which consists of a small numberof frames that are transmitted to a MS with a dormant packet dataservice instance.

Inter-BS Handoff

The MCC 22 supports soft handoff, inter-frequency assignment (FA) hardhandoff and intra-FA hard handoff. The MCC 22 interfaces with the RCC 18to get radio resources as request from the SDU 20 and manages neighborlists.

Inter-CA Hard Handoff

When the MCC 22 receives a handoff request message from the SDU 20 andthe handoff type is inter-CA hard handoff, the MCC 22 sends a HandoffRequired message to the CA 104 to initiate an inter-CA hard handoff as aserving part. If the MCC 22 receives a Handoff Request message from theCA 104, the MCC 22 initiates an inter-CA hard handoff scenario as atarget part.

Terminal Authentication

Terminal authentication is the process by which information is exchangedbetween the MS and the network to confirm the identity of the MS. TheMCC 22 delivers relegated messages to the SDU 20, the RCC 18 and the CA104.

Short Message Service

Short Message Service (SMS) is a mechanism of delivery of short messagesover the mobile network. The MCC 22 supports messages and process forSMS mobile originated calls, SMS mobile terminated calls, and SMSBroadcast calls.

Supplementary Services

The MCC 22 supports various supplementary services including MessageWaiting, Call Forwarding, Call Delivery, Call Transfer, Three WayCalling, and Conference Calling in terms of communicating with the RCC18 using a Feature Notification Message or with the SDU 20 using Flashwith an Information Message.

Test Calls

The MCC 22 initiates the test call process as a request from the basestation manager (BSM 99) or on receiving an Origination Message with alook back service option from the MS.

Call Trace

The MCC 22 initiates the call trace process as a request from the WPM.The MCC 22 stores the related information to a buffer and starts a tracewhenever the MS requests call service.

Selector Distribution Unit (SDU) 20

The SDU 20, which includes an air interface portion that processes airmessages between the SDU and a MS, a router interface portion thatprocesses messages between the SDU and other software blocks, and aportion that processes voice and data calls, is associated with thefollowing functionality:

Multiplex and De-Multiplex

This function multiplexes and de-multiplexes user traffic and signalingtraffic for the air interface.

Forward and Reverse Traffic Frame Selection and Distribution

This function is responsible for selecting the best quality incoming airinterface reverse link frame involved in the soft handoff, anddistributes forward air interface frames to all channel elementsinvolved in a call.

Handoff Type Decision and Handoff Direction

This function decides a handoff type that will be processed includingsoft handoff, softer handoff, hard handoff, etc., and directs handoffprocessing to other software blocks such as the MCC 22 and a trafficchannel element (TCE) in the CEC 16.

Process Radio Link Protocol (RLP) Procedures

A RLP Type 1, 2, and 3 is used with IS-95A/B or cdma2000 trafficchannels to support CDMA data services. The RLP, which is aconnection-oriented, negative-acknowledgement based data deliveryprotocol, provides an octet stream transport service over forward andreverse traffic channels. The RLP includes procedures to reduce theerror rate exhibited by CDMA traffic channels.

Forward and Reverse Power Control

This function generates or utilizes relevant power control informationthat is exchanged over the air interface or the channel element.

Process Test Call Procedures

This function supports an MS loop-back call, such as a service option 2and a service option 9 call.

Process Real Time Protocol (RTP) Procedures

This function is responsible for interfacing with a MG or other BSCs.

Process Signaling Layer 2 Procedures

This function performs the layer 2 functionality of the air interfacesignaling protocol and is responsible for the reliable delivery of thelayer 3 signaling messages between the BSC and the MS.

Process Generic Routing Encapsulation (GRE) Procedures

This function is responsible for interfacing with the PDSN 101.

Media Gateway (G/W) 103

The SDU 20 receives data, formats it and then sends it to the G/W 103.Similarly, data received from the G/W 103 can be formatted by the SDU20.

Signaling Control Connection Part (SCCP) 26

The SCCP 26 is used to provide a referencing mechanism to identify aparticular transaction relating to, for instance, a particular call. Thecurrent implementation of the A1 interface using TCP/IP protocol employsan SCCP implementation which provides the minimal functionality requiredto create the CALL context in which to pass IOS messages and monitor theTCP/IP connection. The SCCP 26 is associated with the followingfunctionality:

TCP/IP Connection Establishment

The SCCP creates a TCP/IP socket as a client to communicate with the CA104.

Signaling Connection Establishment

A new transaction, such as location updating, or an incoming or outgoingcall, is initiated on the radio path. Following an Access Request madeby the MS on the access channel, the connection establishment is theninitiated by the BS.

If the CA 104 decides to perform an inter-CA hard handoff, theconnection establishment is initiated by the CA 104.

Signaling Connection Release

This procedure is normally initiated at the CA 104 but in the case ofabnormal SCCP connection release, the BS may initiate a connectionclearing.

Interoperability System (IOS) 28

The IOS 28 processes messages from the CA 104 or the MCC 22 and convertsbetween internal message format and standard format. A Base StationApplication Part (BSAP) is the application layer signaling protocol thatprovides messaging to accomplish the functions of the A1 Interfacecomponent of the CA—BS Interface. The BSAP is split into twosub-application parts: the BS Management Application Part (BSMAP), andthe Direct Transfer Application Part (DTAP). The BSMAP supports allRadio Resource Management and Facility Management procedures between theCA 104 and the BS, or to a cell(s) within the BS. BSMAP messages are notpassed to the MS, but are used to perform functions at the CA 104 or theBS. A BSMAP message (Complete Layer 3 Information) is also used togetherwith a DTAP message to establish a connection for a MS between the BSand the CA 104, in response to the first layer 3 air interface messagesent by the MS to the BS for each MS system request. The DTAP messagesare used to transfer call processing and mobility management messagesbetween the CA 104 and BS. DTAP messages carry information that isprimarily used by the MS. The BS maps the DTAP messages going to andcoming from the CA from/into the appropriate air interface signalingprotocol.

The IOS 28 is associated with the following functionality:

Encoding Messages

The IOS messages proprietary format from the MCC 22 as the A interfacespecifications for sending to the CA.

Decoding Messages

The IOS 28 converts messages from the CA 104 to internal messages.

Packet Control Function (PCF) 24

The PCF 24 is a packet control function to manage the relay of packetsbetween the BS and the PDSN 101. In a cdma2000 wireless network, accessto packet data services is provided by the PDSN 101. The PCF 24 providescall processing functionality within the Radio Access Network (RAN)interfaces with the PDSN 101 and interfaces with the MCC 22 and the SDU20 to provide internal signaling and packet delivery. The interfacebetween the PCF 24 and the MCC 22 is called the A9 interface and theinterface between the PCF 24 and the SDU 20 is the A8 interface. Theinterface between the PDSN 101 and the PCF 24, which is the interfacebetween the radio and packet network, is known as the R-P interface orthe A10/A11 interface.

The PCF 24 is associated with the following functionality: MainProcessing which creates tasks and receives messages over IP, MessageProcessing which generates and extracts message by packing andunpacking, A10/A11 Processing which processes the A10/A11 interface,A8/A9 Processing which processes the A8/A9 interface, Hash Processingwhich performs the MD5 hashing function, Timer Processing which handlestimer set, timer cancel, and timeout processing, Utility for primitivesand debugging commands, and Call Control for call processing oforiginating, terminated and handoff calls.

Call Agent Simulator (CA_SIM) 30

For wireless voice and data communications, various components, such asthe CA 104 in the core network and the IP-BS in the Radio-AccessNetwork, are necessary components. The installation of other componentsin the core network, such as the CA 104, a HLR, etc., constitutes alarge expense. To increase the efficiency and flexibility, aCA-simulator 30 can be provided so that voice and data calls arepossible without connecting to the CA 104 or to an HLR. As such, anIP-BS can be installed in a small wireless network without a CA or HLR.

Operation, Administration and Maintenance (OAM) 32

The OAM block 32 is associated with the following functionality: aConfiguration Management (CM) block 34 that configures each block ormodule of the BSC 12 based on program load data (PLD) information (whichincludes parameters, such as a system ID, an IP address, etc., toconfigure the system) which can be downloaded from a server, a StatusManagement (SM) block 36 that obtains a status of the BSC 12 and reportsthe status to the BSM 99, and a Fault Management (FM) block 38 thatchecks and detects system faults or alarms and reports them to the BSM.

Referring again to FIG. 1, the radio access network (RAN) 10 furthercomprises a base transceiver station (BTS) 14. The BTS 14 comprises aChannel Element Control (CEC) 16 coupled to the Radio Call Control (RCC)18, an Operation, Administration and Maintenance (OAM) 52 block coupledto the CEC, to the RCC, and to a Transmit and Receive Interface (TRX)40.

The Channel Element Control (CEC) 16

The CEC block 16 controls the call processing to interface with the MS.The CEC also interfaces with upper layer blocks to handle over the airmessages to set-up, maintain, and terminate voice and data calls. Inorder to make these calls, both signaling and traffic frames must betransmitted and received to and from the MS. It is also important forthese frames to be transmitted and received at the right time withcorrect information. This is accomplished by using, for example, a modemchip, such as the Qualcomm CSM5000 modem chip 60, I/F chips 62, atransceiver 64 and a power amplifier 66. The components 60-66 arepredominantly hardware components that can be co-located within the RAN10. The CEC block 16 is associated with the following functionality:

Overhead Channel Configurations

The CEC 16 receives overhead channel configuration messages from the RCMand sets the parameters to the driver of the modem chip 60.

Air Message Encapsulation and Transmission

The CEC 16 encapsulates and sends a frame for sync channel messagetransmission (at, for example, every 80 msec) and sends a frame forpaging channel message transmission (at, for example, every 20 msec). Totransmit each frame of the sync and paging channel, the CEC 16 revokessemaphores periodically by external interrupt request source.

CSM Built-In Test

The CEC 16 provides a built-in test function for the modem chip 60 whichincludes checking a register test, an interrupt test, as well as areverse ARM test. This test can be performed by an operator's request toshow if the modem chip 60 is functioning properly or not.

Forward and Reverse Power Control

The CEC 16 supports forward and reverse power control processing.

Process Time of Day (TOD) Message

The CEC 16 receives the TOD message via a GPS (at, for example, every 2sec) and processes it to get the system time and GPS status.

Process Loopback Call Procedures

This function supports MS-BTS loop-back call, This function can show ifair-interface between MS and BTS works well.

Process Traffic Channel Processing

The CEC 16 is responsible for assigning a traffic channel and clearingit by the order of RCC 18. When the traffic channel is setup, the CEC 16delivers traffic packets between the SDU 20 and the MS.

Maintain Forward and Reverse Link

The CEC 16 checks the forward and reverse path and reports them to astatus or statistics block.

Process High Speed Data Service

The CEC 16 is responsible for processing supplemental channel (SCH)packets for high speed data service which supports up to, for example,128 kbps. The SCH packets are used if additional channels are needed tohandle the transfer of the data.

Process Soft and Softer Handoff Procedure

The CEC 16 is responsible for processing Soft and Softer Handoffs.

Provide H/W Characteristics Test Functionalities

The CEC 16 supports various hardware characteristics tests such as anaccess probe test, a AWGN test, etc. Theses tests determine if the RF orthe IF properties of each of the basestations are in order to ensure(via, for example, a good path) that messages can be transferred.

The CSM application 48 is adapted to receive data from the CSM (or modemchip 60) Driver 50.

Radio Call Control (RCC) 18

The call control of the air interface is provided by the RCC 18. The airinterface between the MS and the BTS 14 is specified by, for example,the TIA/EIA-95-A/B and the cdma2000 standards, which include the coreair interface, minimum performance, and service standards. Thefunctionalities of the RCC 18 consist of call processing, resourcemanagement, and supplementary services. The RCC 18 provides callprocessing functionality in order to setup and release call and resourcemanagement of radio resources such as CDMA channels, traffic channelelements, Walsh code channels, frame offsets, etc. The RCC 18 alsoprovides signaling functionality by interfacing with other relevantsoftware blocks.

The RCC 18 provides various processing functions including: MainProcessing which creates tasks and receives messages over IP, ResourceManagement which processes resource allocation and de-allocation,Message Processing which generates and extracts message by packing andunpacking, Initialization Processing which initializes buffers andvariables, RCV. from RSCH processing which processes all messages on thereverse common signaling channel, RCV. from RDCH processing whichprocesses some messages on the reverse dedicated signaling channel, RCV.from MCC processing which processes all messages from the MCC, SND. toFSCH processing which processes all messages sent to MS on the forwardcommon signaling channel, SND. to FDCH processing which processes somemessages sent to MS and CEC on forward dedicated signaling channel, SND.to MCC processing which processes all messages sent to the MCC, Layer 2Processing which processes Layer 2 information, Hash Processing whichperforms the hash function to decide CDMA channel and Paging Channelnumber, Timer Processing which handles timer set, timer cancel, andtimeout processing, and Utility which provides primitives and debuggingcommands.

Transmit and Receive Interface (TRX) 40

The TRX block 40 controls and diagnoses hardware devices in the BTS 14,and includes:

The PUC/PDC Block 42

The PUC/PDC 42 up-converts and down-converts between a baseband signaland an IF signal.

The Transceiver Control (XCVR) Block 44

The Transceiver Control Block (XCVR) 44 controls transceiver operationswhich carry IF signals to a carrier frequency band.

AMP Control Block

For high power amplification of the signal, the IP-BS provides theinterface to the AMP. The AMP control block controls AMP operations suchas ON/OFF.

Hardware Diagnostic Test Module

The diagnostic test module provides the functionalities for hardwarecharacteristics test of pn3383 such as AWGN test, access probe test,etc. For example, the pn3383 test implements test environmentconditions.

The power amplifier (PA) 66, via the RRCU 46, amplifies the outputsignal because the output of the XCVR 44 tends to be small. As such, abroader coverage area is possible.

Operation, Administration and Maintenance (OAM) Block 52

The OAM block 32 is associated with the following functionality: aConfiguration Management (CM) block 34 that configures each block ormodule of the BTS 14 based on program load data (PLD) information (whichincludes parameters, such as a system ID, an IP address, etc., toconfigure the system) received from the BSM (or IP-BS) 99, a StatusManagement (SM) block 36 that obtains a status of the BTS 14 and reportsthe status to the BSM, and a Fault Management (FM) block 38 that checksand detects system faults or alarms and reports them to the BSM.

Referring now to FIG. 2, the components of a stackable IP Radio AccessNetwork (RAN) 70 are depicted. The blocks in the RAN 70 perform asimilar functionality to their respective blocks in the RAN 10. Such astackable RAN 70 provides increased bandwidth and redundancy withoututilizing a card based expansion scheme as has been previously employed.Rather, the RAN 70 is modular and stackable (in a very small footprint)and includes a control portion (the Main Control Processor (MCP)) 72 anda device portion (the SDU/CEC Processor (SCP)) 74. With a centralizedcontrol portion 72, various device portions 74 can be utilized with asingle control portion.

A difference between the RAN 70 and the RAN 10 is that the SDU 20 is nowco-located with the CEC 16, and the RCC 18 is co-located with the MCC22. As such, messaging between these co-located blocks is decreasedproviding an increase in system performance.

Referring now to FIG. 3, a stackable configuration 80 of the RAN of thepresent invention is depicted. The configuration 80 includes a RAN 70that includes a master MCP 72 and a RAN 70′ that includes a slave MCP72. The master and slave MCPs preferably have the same IP address forredundancy. If the master MCP fails, a seamless transition to the slaveMCP occurs. Backhaul timing is a limited issue because information istransferred between a BTS and a BSC in one “box” and not across a longerdistance as with a typical network. The configuration 80 furtherincludes RANs 76 which do not contain an MCP but rather, are controlledby the master MCP 72 in RAN 70. Each of the RANs depicted 70, 70′, and76 include at least one transceiver 64, power supply 82, and GPSreceiver 92 that synchronizes the timing between the BSC 12 and the BTS14 and between the MCP 72 and the SCP 74 per information received from adatabase 91 and/or GPS related satellites.

The configuration 80 may also include a combiner 86 that may combine aplurality of frequency segments to a common transmission line orantenna, a power amplifier 88 (which is similar to power amplifier 66),and a power supply 90 that could be used to re-set or re-start the RANs70, 70′, and 76. A switch hub 84 may be included to provide a singleaccess (via, for example, an IP address), between the configuration 80and the IP network 92.

Referring now to FIG. 4, a mobile origination message flow 100 isdepicted. The RCC 18 receives an Origination message 106 from the MS 102through the CEC 16 with access information, the MS identification,service option, and other call related information. The RCC 18 unpacksthe message 106 and stores significant call related information forfurther processing, and sends a Base Station Acknowledgement message 108to the MS 102 and an origination message 110 to the MCC 22 with the MSidentification information.

The MCC 22 constructs the CM Service Request message 112 (based on theIS-2001-B specification), places it in the Complete Layer 3 Informationmessage, and sends the message to the CA 104. The MCC 22 receives anAssignment Request message 114 from the CA 104 and allocates the SDU ID,IP address and port number for the A2 (RTP) interface and sends anAssignment Request message 116 to the RCC 18 to request an assignment ofradio resources. This message 116 includes information on the SDU 20,resource information for A.sub.bis interface, Service Option, the MSidentification, etc.

Upon receiving Assignment Request Message 116 from the MCC 22, the RCC18 allocates radio resources and then sends a Traffic Channel Assignmessage 118 with assign type (=NEW) to the CEC 16 in order to assignForward and Reverse Traffic Channel Elements. The RCC 18 sends theTraffic Channel Assign message 120 with traffic channel allocationinformation to the MCC 22. When the CEC 16 receives Tc_Mobile_Assignmessage 118 from the RRC 18, it sets CSM driver with the parameters inthe message to activate the CSM ASICs to prepare call setup. The CEC 16sends null traffic frame 122 to the Mobile Station 102 and a OTA_TX_ONmessage 124 (that CEC 16 is sending null frame to MS 102) to the RCC 18.The RCC 18 makes and sends an Extended Channel Assignment Message 126 tothe MS 102 through the CEC 16.

After receiving the TC assign message from the RCC 18 with the result ofASSIN_OK or ASSIGN_ALTERNATIVE, the MCC 22 sends a Call_Setup_Cs message128 to the SDU 20 with the information on the MS 102 as well as the BTSresource to SDU 20 for initialization. The SDU 20 receives theCall_Setup_Cs message 128 that is sent from the MCC 22 to request forselector initialization, and sends a Link_Active_Se message 130 with SDU20 resource information to the CEC 16. When the CEC 16 receives theLink_Active_Se message 130 from the SDU 20, the CEC 16 assumes that thelink between the CEC 16 and the SDU 20 has been established and sends aLink_Act_Ack_Es message 312 to the SDU 20 to acknowledge the receipt ofthe Link_Active_Se message 130.

Upon acquiring the signal 134 of the MS 102, the CEC 16 sends aSEL_LINK_ON message 136 which indicates Call setup is complete to theRCC 18, which updates the call state with Active (BUSY). When the CEC 16acquires the signal of the MS 102, it sends a Mob_Acquire_Es message 138to the SDU 20, which indicates the reverse traffic channel has beenestablished. Once the SDU 20 acquires the reverse traffic channel, itsends a Forward Traffic message 140, including a Base StationAcknowledgement Order with layer 2 acknowledgement required, to the MS102 over the forward traffic channel.

Upon receiving an Ack Order Message 142 from the MS, the SDU 20 sends aService Connect Message 144 with layer 2 acknowledgement required to theMS 102 over the forward traffic channel. The SDU 20 receives a ServiceConnect Completion message 146 from the MS 102 and then sends a MobileConnect message 148 to the MCC 22 to indicate the MS 102 connection. TheMCC 22 sends an Assignment Complete message 150 to the CA 104 and it mayinclude SDU 20 resource information for the A2 interface. The MCC 22 mayreceive a Progress message 152 from the CA 104 including a destinationIP address and port number for the A2 interface and a Pstn_Info_Csmessage 154 is sent to the SDU 20. The SDU 20 receives the Pstn_Info_Csmessage 154 with the PSTN connect information and starts traffic packetprocessing for conversation.

Referring now to FIG. 5, a mobile termination message flow 200 isdepicted. The MCC 22 receives a Paging Request message 202 from the CA104 and sends a Paging Request message 204 to the RCC 18. The RCC 18receives the paging request from the MCC 22 with MSID information andtags and stores them for further processing. The RCC 18 determines pagedfrequency assignment (FA) by using the Hash Function with MSIDinformation, and sends a General Page message 206 to the MS 102 throughthe CEC 16.

The RCC 18 receives a Page Response message 208 from the MS 102 throughthe CEC 16 (with access information, the MS identification, serviceoption, and other call related information), unpacks the message andstores significant call related information for further processing, andsends a Base Station Acknowledgement message 210 to the MS 102. The RCC18 sends a page response message 212 with the MS identificationinformation and specified tag to the MCC 22, which constructs a PageResponse message 214 based on the IS-2001-B specification, places it ina Complete Layer 3 Information message, and sends the message to the CA104.

The MCC 22 receives an Assignment Request message 216 from the CA 104which may include a destination IP address and port number for the A2interface. The MCC 22 allocates a SDU ID, IP address and port number forthe A2 (RTP) interface, sends an Assignment Request message 218 to theRCC 18 to request an assignment of radio resources. This messageincludes information on the SDU 20 resource information for A.sub.bisinterface, Service Option, MS identification, etc. After receiving theAssignment Request message 218 from the MCC 22, the RCC 18 allocatesradio resources and then sends a Traffic Channel Assign message 220 withassign type (=NEW) to the CEC 16 in order to assign Forward and ReverseTraffic Channel Elements. The RCC 18 sends a TC assign message 224 withtraffic channel allocation information to the MCC 22.

When the CEC 16 receives the Tc_Mobile_Assign message 220 from the RCC18, it sets a CSM driver with the parameters in the message to activatethe CSM ASICs to prepare call setup. The CEC 16 sends a null trafficframe 226 to the MS 102 and sends a OTA_TX_ON message 228 (thatindicates the CEC 16 is sending null frame to the MS 102) to the RCC 18.The RCC 18 makes and sends an Extended Channel Assignment message 230 tothe MS 102 through the CEC 16. After receiving the TC assign messagefrom the RCC 18 with the result of ASSIN_OK or ASSIGN_ALTERNATIVE, theMCC 22 sends a Call_Setup_Cs message 232 with the information on the MS102 as well as a BTS resource to the SDU 20 for initialization.

The SDU 20 receives a Call_Setup_Cs message that is sent from the MCC 22to request selector initialization. The SDU 20 sends a Link_Active_Semessage 234 with the SDU 20 resource information to the CEC 16, whichassumes that the link between the CEC 16 and the SDU 20 has beenestablished and sends a Link_Act_Ack_Es message 236 to the SDU 20 toacknowledge the receipt of the Link_Active_Se message 234. Uponacquiring the signal 238 of the MS 102, the CEC 16 sends a SEL_LINK_ONmessage 240 which indicates Call setup is completed to the RCC 18. TheRCC 18 updates call state with Active (BUSY), and the CEC 16 sends aMob_Acquire_Es message 242 to the SDU 20, which means the reversetraffic channel established. Once the SDU 20 acquires the reversetraffic channel, it sends a Forward Traffic message 244 including a BaseStation Acknowledgement Order with layer 2 acknowledgement required, tothe MS 102 over the forward traffic channel. Upon receiving the MS 102Ack Order message 246 from the MS 102, the SDU 20 sends a ServiceConnect message 248 with layer 2 acknowledgement required to the MS 102over the forward traffic channel.

The SDU 20 receives a Service Connect Completion message 250 that issent from the MS 102 and then sends a Mobile Connect message 252 to theMCC 22 to indicate the MS 102 connection. The MCC 22 sends an AssignmentComplete message 254 to the CA 104, which may include the SDU 20resource information for the A2 interface. An Alert Message 256 is sentfrom the MCC 22 to cause ringing at the MS 102. The SDU 20 sends anAlert With Information message 258 to the MS 102 to cause ringing at theMS 102. This message is sent by the SDU 20 to the Traffic Channel in theForward Traffic message. When the call is answered 260 at the MS 102, aConnect Order 262 with acknowledgment required is transmitted to the SDU20 through the CEC 16 (reverse traffic channel). The SDU 20 sends aConnect_Sc message 264 to the MCC 22 to acknowledge a connection betweenthe SDU 20 and the MS 102. The MCC 22 sends a Connect message 266 to theCA 104 and a Pstn_Info_Cs message 268 to the SDU 20 with the PSTNconnect information and starts traffic packet processing forconversation.

Referring now to FIGS. 6A and 6B, a mobile to mobile call setup andrelease message flow 300 is depicted. The messaging 106-268 as describedin FIGS. 4 and 5 leads to a Conversation State 301. The MS 102 initiatesa call clearing by transmitting a Release Order message 302 over thereverse traffic channel. The SDU 20 acknowledges the MS 102 by sending aRelease Order message 304 over the forward traffic channel.

The SDU 20 sends a forward control message containing the Release Ordermessage 304 to release the call in BTS. This message may beretransmitted a number of times. When the CEC 16 receives aCtl_Release_Se message 306 from the SDU 20, it responds 308 that callrelease was successfully performed. The CEC 16 stops the forward andreserves traffic service and sends a Release message 310 to the RCC 18in order to request a release traffic channel. The RCC 18 receives aCall Release message from the CEC 16 and releases the originated call.The RCC 18 de-allocates all the resources and initializes the resourcebuffer and call buffer related to the call. The RCC 18 sends a Releasemessage 312 to the CEC 16 to initialize the specified Forward andReverse Traffic Channel Elements.

Upon receiving the TC Release message 312 from the RCC 18, the CEC 16shuts down traffic channel operations. When a Ctl_Rel_Ack_Es message forresponse from the CEC 16 is received, the SDU 20 sends a Release message314 to the MCC 22 to request the call to be released in the BSC. The MCC22 requests a call release 316 to the CA 104 which orders the callrelease by sending Clear Command messages 318 a-318 b to the MCC 22. TheMCC 22 of the origination side sends a Rel_Cmpl_Cs message 320 to theSDU 20 to acknowledge the call release, and the MCC 22 of thetermination side sends a Relealse_Cs message 322 to the MCC 22 torequest the call release of the terminated call. Upon receiving theRelease Completion message from the MCC 22, the SDU 20 stops allprocessing for this call 338.

Although an exemplary embodiment of the system of the present inventionhas been illustrated in the accompanied drawings and described in theforegoing detailed description, it will be understood that the inventionis not limited to the embodiments disclosed, but is capable of numerousrearrangements, modifications, and substitutions without departing fromthe spirit of the invention as set forth and defined by the followingclaims. For example, the capabilities of the invention can be performedfully and/or partially by one or more of the modules RANs 70, 70′, and76, and/or by one or more of the blocks 16-58. Also, these capabilitiesmay be performed in the current manner or in a distributed manner andon, or via, any device able to transfer information between the RANs,the blocks, and/or other components. Further, although depicted in aparticular manner, various blocks may be repositioned without departingfrom the scope of the current invention. For example, the RCC 18 may bepositioned in the BSC 12, while the SDU 20 may be positioned in the BTS14. Still further, although depicted in a particular manner, a greateror lesser number of RANs and/or blocks may be utilized without departingfrom the scope of the current invention. For example, additional RANs 76may be utilized in the configuration 80 of the present invention.

Further, a lesser or greater number of messages may be utilized with thepresent invention and such messages may include complementaryinformation in order to accomplish the present invention, to provideadditional features to the present invention, and/or to make the presentinvention more efficient. Also, various timers may be employed by thepresent invention. For example, in the case of the mobile terminationmessage flow, when the MCC 22 constructs the Page Response message 214based on the IS-2001-B specification, places it in the Complete Layer 3Information message, and sends the message to the CA 104, it may furtherstart timer T.sub.303. Then, when the MCC 22 receives an AssignmentRequest message 216 from the CA 104, it may stop the T.sub.303 timer.

What is claimed is:
 1. A method, comprising: receiving an originationrequest message by a main call control (MCC) from a radio call control(RCC), the origination request message originating from a mobile stationand being forwarded via the RCC to the MCC; receiving a traffic channelassign message by a channel element control (CEC) and by the MCC fromthe RCC, wherein the assign message includes a request for an assignmentof radio resources; receiving a call setup message by a selectordistribution unit (SDU) from the MCC; receiving a mobile station signalat the CEC; transmitting a call setup complete message to the RCCresponsive to receiving the mobile station signal; transmitting, via theSDU, a forward traffic message comprising a base station acknowledgmentorder to the mobile station over a forward traffic channel; andreceiving a service connect completion message at the SDU from themobile station.
 2. The method of claim 1 comprising receiving a mobileacquire message by the SDU from the CEC.
 3. The method of claim 1,wherein the MCC and the RCC located in a Main Control Processor.
 4. Themethod of claim 1 comprising sending a service connect message from theSDU to the mobile.
 5. The method of claim 1 comprising receiving amobile connect message by the MCC from the SDU.
 6. The method of claim 1comprising receiving a PSTN information message by the SDU from the MCC.7. The method of claim 1, wherein the origination request messagecomprises identification information of the mobile station.
 8. Themethod of claim 1, wherein the CEC and the MCC are included in at leastone of a base station controller and a base transceiver station.
 9. Themethod of claim 1, wherein the traffic channel assign message receivedby the CEC assigns forward and reverse traffic channel elements.
 10. Themethod of claim 1, wherein the traffic channel assign message receivedby the MCC includes traffic channel allocation information.
 11. Themethod of claim 1, wherein the call setup message received by the SDUincludes information related to the mobile and to initializationinformation.
 12. The method of claim 1, further comprising receiving alink active message by the CEC from the SDU, wherein the link activemessage received by the CEC indicates a link between the CEC and the SDUhas been established.
 13. The method of claim 2, wherein the mobileacquire message received by the SDU occurs when the CEC acquires thesignal of the mobile and indicates the reverse traffic channel has beenestablished.
 14. The method of claim 3, wherein the forward trafficmessage sent from the SDU comprises a layer 2 acknowledgement over aforward traffic channel.
 15. The method of claim 5, wherein the mobileconnect message received by the MCC indicates a connection of themobile.
 16. The method of claim 1, further comprising receiving PSTNinformation by the SDU, wherein the PSTN information message received bythe SDU includes PSTN connect information and starts traffic packetprocessing for conversation.
 17. The method of claim 1 comprisingreceiving a link active message by the CEC from the SDU, the CEC and theSDU located in a SDU/CEC Processor (SCP).
 18. The method of claim 1comprising receiving an assignment request message by the RCC from theMCC.
 19. A non-transitory computer readable storage medium comprisinginstructions for: receiving an origination request message by a maincall control (MCC) from a radio call control (RCC), the originationrequest message originating from a mobile station and being forwardedvia the RCC to the MCC; receiving a traffic channel assign message by achannel element control (CEC) and by the MCC from the RCC; receiving acall setup message by a selector distribution unit (SDU) from the MCC;receiving a mobile station signal at the CEC; transmitting a call setupcomplete message to the RCC responsive to receiving the mobile stationsignal; transmitting via the SDU a forward traffic message comprising abase station acknowledgment order to the mobile station over a forwardtraffic channel; and receiving a service connect completion message atthe SDU from the mobile station.
 20. A system, comprising: a main callcontrol (MCC) located in a Main Control Processor (MCP) adapted toreceive an origination request message, the origination request messageoriginating from a mobile station and being forwarded via an radio callcontrol (RCC) to the MCC; at least one channel element control (CEC) anda main call control (MCC) adapted to receive a traffic channel assignmessage; and at least one selector distribution unit (SDU) adapted toreceive a call setup message; wherein the CEC is adapted to receive amobile station signal, wherein the CEC is adapted to transmit a callsetup complete message to the RCC responsive to receiving the mobilestation signal, wherein the SDU is adapted to transmit a forward trafficmessage comprising a base station acknowledgment order to the mobilestation over a forward traffic channel, and wherein the SDU is adaptedto receive a service connect completion message from the mobile station.